Summary

The published .d.ts of three compound components — @commercetools-uikit/constraints, @commercetools-uikit/radio-input, and @commercetools-uikit/view-switcher — leak a reference to the aggregate preset package:

// before (20.6.0 / 20.6.1)
Group: { (props: import("@commercetools-frontend/ui-kit").TGroupProps): JSX.Element; … }

Strict-TS consumers that install only the granular @commercetools-uikit/* packages don't have @commercetools-frontend/ui-kit, so the reference resolves to any, contextual handler typing is lost, and noImplicitAny flags it as TS7006 — on what looks like a routine minor bump. This was discovered downstream in commercetools/identity#757 (RadioInput.Group onChange handlers).

Root cause

Not an API change — source is byte-identical and tsc alone emits the correct relative specifier. With preserveSymlinks: false (set in FEC-935 so typecheck resolves @storybook/* subpaths), TypeScript's declaration emit follows pnpm's symlinks, discovers that the leaf type is also reachable through the node_modules package @commercetools-frontend/ui-kit (which re-exports it), and prefers the bare node_modules specifier over the relative path — a deliberate, long-standing TypeScript behavior.

That package is only present in node_modules because it became a root devDependency (added in FEC-938 so the .visualroute/bundlespec fixtures resolve under strict pnpm). Verified by toggling the single variable — with the symlink present the emit leaks; with it removed (everything else held constant, including preserveSymlinks: false) the emit is correct:

Fix (minimally invasive)

Belt and suspenders:

• The belt — scripts/build.sh hides the meta-package symlink for the preconstruct build step only (preconstruct doesn't need it — the fixtures aren't part of the dts program), then restores it (trap-guarded so it's restored even if the build fails). No source, component API, or preserveSymlinks change; the .visualroute/bundlespec fixtures are untouched.
• The suspenders — after emit, the build asserts that no granular package's published declarations reference the aggregate preset by its bare specifier, and fails the build if one does. This future-proofs the workaround against being dropped, preconstruct changing its resolution, or a new compound component reintroducing the pattern. The check uses find (not a ** glob) so it covers packages at every nesting depth.

This is the smallest change that produces correct published types, and it's the right trade-off for a legacy codebase: it touches one build script and leaves every TypeScript config, dependency, and source file exactly as it is.

Alternatives considered (and why not)

paths cannot fix this — TypeScript's paths changes module resolution, never declaration emit. The two structural options were both heavier and were rejected:

• Flip preserveSymlinks: true (globally, or via a dedicated emit tsconfig). It does fix the specifier, but it reintroduces the full FEC-935 typecheck breakage (~270 errors, including in published component source, not just stories), so it breaks pnpm typecheck and the IDE. Decoupling it for emit-only isn't clean either: preconstruct requires a custom-named tsconfig to exist in every package directory (it doesn't walk up to the root), and VS Code can't be pointed at a non-default tsconfig — so the editor would still surface the ~270 errors.
• Remove the root @commercetools-frontend/ui-kit devDependency and repoint the 71 .visualroute/bundlespec fixtures off the aggregate onto granular packages. This is the most structurally "correct" fix (the symlink would never exist), but it's 71 mechanical edits plus a Percy visual-regression re-run — disproportionate to a one-line build-step problem.

The chosen fix implements the same underlying strategy as the structural option — keep the aggregate package out of the leaf packages' declaration-emit graph — but does it at build time with no churn.

Known limitation

A bare pnpm preconstruct build run outside scripts/build.sh would still leak, and the regression guard only runs as part of scripts/build.sh. The release path goes through pnpm build, so published artifacts are both fixed and guarded.

Verification

Full pnpm build run on this branch:

• ✅ build green; meta-package symlink restored afterward
• ✅ leaked specifiers across the whole published cohort: 0 (was 3)
• ✅ the 3 packages now emit relative specifiers:
  • radio-input → import("./radio-group.js").TGroupProps, import("./radio-option.js").TOptionProps
  • constraints → import("./horizontal/index.js").THorizontalProps
  • view-switcher → import("./view-switcher.js").TViewSwitcherProps
• ✅ regression guard tested both ways: passes on the fixed dist, and fails the build (naming the offending file) when a leak is injected

Release

Patch changeset included. The cohort is a fixed changeset group, so the whole 20.6.x line republishes together — every package is rebuilt with the fixed build, so the fix propagates cohort-wide.

Refs: commercetools/identity#757